Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80d204e412a1c33213c86fb256b4b1269715f7928749643adb6b4017cdbb6f03

Tx prefix hash: 029c28750f78a1d7a8c46f98d5040ed410292a15b2946e31d4ba86a4d5749e5a
Tx public key: 985b09d7940c260b72dc9940f7e4a32166f2201dde1dcc20969f9a64c150a741
Timestamp: 1578884665 Timestamp [UCT]: 2020-01-13 03:04:25 Age [y:d:h:m:s]: 04:352:00:49:26
Block: 44324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1141145 RingCT/type: yes/0
Extra: 01985b09d7940c260b72dc9940f7e4a32166f2201dde1dcc20969f9a64c150a74102110000000c4ac5aa02000000000000000000

1 output(s) for total of 437.660174856000 dcy

stealth address amount amount idx
00: efee5289847ec54bc0ae4df885c8073748dafdb187cc723a3c34f10097fdf75f 437.660174856000 80631 of 0

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": 44334, "vin": [ { "gen": { "height": 44324 } } ], "vout": [ { "amount": 437660174856, "target": { "key": "efee5289847ec54bc0ae4df885c8073748dafdb187cc723a3c34f10097fdf75f" } } ], "extra": [ 1, 152, 91, 9, 215, 148, 12, 38, 11, 114, 220, 153, 64, 247, 228, 163, 33, 102, 242, 32, 29, 222, 29, 204, 32, 150, 159, 154, 100, 193, 80, 167, 65, 2, 17, 0, 0, 0, 12, 74, 197, 170, 2, 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