Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71b3264cc428e79d7c76e1665dd33d1610fc5d682f8c3f34e7a6bfe01bc829fb

Tx prefix hash: a695fa200278c3a5ace59391ca891a8d282519c6a60b6527f664e49663a2bb27
Tx public key: 1d86ae91dbcd81310c3cc493684d1845e2d0de21fa0a109461e9d308efcdbd7c
Timestamp: 1578836917 Timestamp [UCT]: 2020-01-12 13:48:37 Age [y:d:h:m:s]: 04:298:15:02:11
Block: 44008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1102845 RingCT/type: yes/0
Extra: 011d86ae91dbcd81310c3cc493684d1845e2d0de21fa0a109461e9d308efcdbd7c0211000000174ac5aa02000000000000000000

1 output(s) for total of 438.716601796000 dcy

stealth address amount amount idx
00: 7557e6c7919186019527dcb09d521958b887ae9cf3b6e698f1b684c6c513a3f6 438.716601796000 79935 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": 44018, "vin": [ { "gen": { "height": 44008 } } ], "vout": [ { "amount": 438716601796, "target": { "key": "7557e6c7919186019527dcb09d521958b887ae9cf3b6e698f1b684c6c513a3f6" } } ], "extra": [ 1, 29, 134, 174, 145, 219, 205, 129, 49, 12, 60, 196, 147, 104, 77, 24, 69, 226, 208, 222, 33, 250, 10, 16, 148, 97, 233, 211, 8, 239, 205, 189, 124, 2, 17, 0, 0, 0, 23, 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