Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f63935f10bbfbcaa5dc9ed386474fd2850eaa2f7bace141222332db5172e0d3

Tx prefix hash: 771cf1a64fada6df69f00a5dd92a6f0df6192b33124d8644002bc53f32611679
Tx public key: ebc8101375d501c008aaef5ae607908071edf7d70403dc5bc2cbf940071ee1e8
Timestamp: 1577929561 Timestamp [UCT]: 2020-01-02 01:46:01 Age [y:d:h:m:s]: 04:329:14:54:50
Block: 36810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124714 RingCT/type: yes/0
Extra: 01ebc8101375d501c008aaef5ae607908071edf7d70403dc5bc2cbf940071ee1e802110000000ef422c868000000000000000000

1 output(s) for total of 463.483247995000 dcy

stealth address amount amount idx
00: ba9a054523465e563bf76cc70bb743631792f67f5ae64cfae82a2592db710090 463.483247995000 62410 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": 36820, "vin": [ { "gen": { "height": 36810 } } ], "vout": [ { "amount": 463483247995, "target": { "key": "ba9a054523465e563bf76cc70bb743631792f67f5ae64cfae82a2592db710090" } } ], "extra": [ 1, 235, 200, 16, 19, 117, 213, 1, 192, 8, 170, 239, 90, 230, 7, 144, 128, 113, 237, 247, 215, 4, 3, 220, 91, 194, 203, 249, 64, 7, 30, 225, 232, 2, 17, 0, 0, 0, 14, 244, 34, 200, 104, 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