Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9da732e512097718f60cc59885f2716b6fe94f7f4d95d95032e1dc6a37c46845

Tx prefix hash: 84540e59d0b95103f17387ea8d5c4bc78961376b1f6912f203b666310f9f6bb1
Tx public key: d9f5099ebbfbe23f14261e7952f3c28d8790e71e4ba58403f84dff9745c826e4
Timestamp: 1723374888 Timestamp [UCT]: 2024-08-11 11:14:48 Age [y:d:h:m:s]: 00:305:03:08:07
Block: 1085540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217967 RingCT/type: yes/0
Extra: 01d9f5099ebbfbe23f14261e7952f3c28d8790e71e4ba58403f84dff9745c826e4021100000012e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b5063ca4e4e4428c483ec96c5f88609a70dd405a444af2fb925f4bb64f8e683 0.600000000000 1560127 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": 1085550, "vin": [ { "gen": { "height": 1085540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b5063ca4e4e4428c483ec96c5f88609a70dd405a444af2fb925f4bb64f8e683" } } ], "extra": [ 1, 217, 245, 9, 158, 187, 251, 226, 63, 20, 38, 30, 121, 82, 243, 194, 141, 135, 144, 231, 30, 75, 165, 132, 3, 248, 77, 255, 151, 69, 200, 38, 228, 2, 17, 0, 0, 0, 18, 233, 20, 221, 21, 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