Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34eb3bfd050810e0c61c2d61239fece86b1d7a3f2d28ad206dd3d712a5071207

Tx prefix hash: f5455789d9cd8977f48759fdacdc3c8cce495a646422376e00abfee8d22d422d
Tx public key: 3c42f155e5d9e1a99c7817e465763831fdf34d56725f49a7d2dc15930577d930
Timestamp: 1720569679 Timestamp [UCT]: 2024-07-10 00:01:19 Age [y:d:h:m:s]: 01:123:15:45:59
Block: 1062287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346895 RingCT/type: yes/0
Extra: 013c42f155e5d9e1a99c7817e465763831fdf34d56725f49a7d2dc15930577d93002110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0678d1c47d33cf187481923e3a182d204a27dc7097112bc29f08d2db697d5b1 0.600000000000 1532788 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": 1062297, "vin": [ { "gen": { "height": 1062287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0678d1c47d33cf187481923e3a182d204a27dc7097112bc29f08d2db697d5b1" } } ], "extra": [ 1, 60, 66, 241, 85, 229, 217, 225, 169, 156, 120, 23, 228, 101, 118, 56, 49, 253, 243, 77, 86, 114, 95, 73, 167, 210, 220, 21, 147, 5, 119, 217, 48, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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