Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc7404e1eca1ff793ee930f97b5245ac16eba9eee2d594f247f7b4b519ffdb61

Tx prefix hash: b2cbf303aaa12183fb6711ff193981896b80483038c580f8273dcbdaa5179665
Tx public key: e5d0e9941624d4af68c39925aabfa525061261380b33e4ff293ec7ddfeaef554
Timestamp: 1574465706 Timestamp [UCT]: 2019-11-22 23:35:06 Age [y:d:h:m:s]: 05:037:14:33:13
Block: 14855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1170198 RingCT/type: yes/0
Extra: 01e5d0e9941624d4af68c39925aabfa525061261380b33e4ff293ec7ddfeaef55402110000000166a80d00000000000000000000

1 output(s) for total of 547.999424965000 dcy

stealth address amount amount idx
00: 7b0a521cbbbe1634c01c4a786cf5eaa9d72d72d35f9dda0a9a364cacb614287f 547.999424965000 19299 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": 14865, "vin": [ { "gen": { "height": 14855 } } ], "vout": [ { "amount": 547999424965, "target": { "key": "7b0a521cbbbe1634c01c4a786cf5eaa9d72d72d35f9dda0a9a364cacb614287f" } } ], "extra": [ 1, 229, 208, 233, 148, 22, 36, 212, 175, 104, 195, 153, 37, 170, 191, 165, 37, 6, 18, 97, 56, 11, 51, 228, 255, 41, 62, 199, 221, 254, 174, 245, 84, 2, 17, 0, 0, 0, 1, 102, 168, 13, 0, 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