Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fead9c06ed954a1efbd35d40a481d07c537c2cb0fceb4f68fd7327b4d24f2ff

Tx prefix hash: 8e5abc62d9a5d663c2ef849138adb7198b583715e52ae4f7eee4f67cbd68ba19
Tx public key: 3a676d72b87a14109f672a819be8114e72a7c529f8869269997d54ad83241b85
Timestamp: 1735618801 Timestamp [UCT]: 2024-12-31 04:20:01 Age [y:d:h:m:s]: 00:357:15:15:46
Block: 1186907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253162 RingCT/type: yes/0
Extra: 013a676d72b87a14109f672a819be8114e72a7c529f8869269997d54ad83241b85021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e47a6a4e3c0de8fc8d133788ca5f99c65af7bc3a3cbe558dd8cfe25a54ee9fc 0.600000000000 1673392 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": 1186917, "vin": [ { "gen": { "height": 1186907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e47a6a4e3c0de8fc8d133788ca5f99c65af7bc3a3cbe558dd8cfe25a54ee9fc" } } ], "extra": [ 1, 58, 103, 109, 114, 184, 122, 20, 16, 159, 103, 42, 129, 155, 232, 17, 78, 114, 167, 197, 41, 248, 134, 146, 105, 153, 125, 84, 173, 131, 36, 27, 133, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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