Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a75da1bbcce5ae5c4a876ceaecc926843d3bd335678bec00962d4ea37d01b8d4

Tx prefix hash: 05eb1ce22239db7de8ec364f21c0de573765604b1d6c8c51b5a89d21758d1cb8
Tx public key: d484c0037f2677dd59f3d0d6c89438d0854871e379370e3cb575e5c682fe11da
Timestamp: 1702684314 Timestamp [UCT]: 2023-12-15 23:51:54 Age [y:d:h:m:s]: 02:038:02:09:53
Block: 913990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546907 RingCT/type: yes/0
Extra: 01d484c0037f2677dd59f3d0d6c89438d0854871e379370e3cb575e5c682fe11da02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd401d83e259224b605543959297f4d03ef809b7f4cbedc3c081c7bcb84cc4b8 0.600000000000 1371270 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": 914000, "vin": [ { "gen": { "height": 913990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd401d83e259224b605543959297f4d03ef809b7f4cbedc3c081c7bcb84cc4b8" } } ], "extra": [ 1, 212, 132, 192, 3, 127, 38, 119, 221, 89, 243, 208, 214, 200, 148, 56, 208, 133, 72, 113, 227, 121, 55, 14, 60, 181, 117, 229, 198, 130, 254, 17, 218, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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