Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f231810063041d60952e1bee77236659efc1f04f6c82b74a9ea0b0831900b0c2

Tx prefix hash: 73d87e7b3aa326099e9ea6ae09715dc4ab16fb25a5088020e6c41c5dde4ec7fb
Tx public key: 67a3fe4199618170eee5e05f402626e585a65644ae8f2d92ba0133544c8e38cc
Timestamp: 1718662435 Timestamp [UCT]: 2024-06-17 22:13:55 Age [y:d:h:m:s]: 00:295:13:40:08
Block: 1046467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211221 RingCT/type: yes/0
Extra: 0167a3fe4199618170eee5e05f402626e585a65644ae8f2d92ba0133544c8e38cc02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0408d3884af9ee3d28835f578d13929a53f24e2158c7c4205dfa8d8bc45f661e 0.600000000000 1516280 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1046477, "vin": [ { "gen": { "height": 1046467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0408d3884af9ee3d28835f578d13929a53f24e2158c7c4205dfa8d8bc45f661e" } } ], "extra": [ 1, 103, 163, 254, 65, 153, 97, 129, 112, 238, 229, 224, 95, 64, 38, 38, 229, 133, 166, 86, 68, 174, 143, 45, 146, 186, 1, 51, 84, 76, 142, 56, 204, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8