Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a79d139179a7dff6da6db6b9da6dcb6fc95acad27b5bb39cbdcdd1ed149424f

Tx prefix hash: 17cf570ed41847e88dfd30161322504f0cf2784a5d7d322e1ed733ead6722737
Tx public key: a4676c70f26213d91c81922502b507711b04c2413470f1bf2afa611cf4917c5c
Timestamp: 1713377093 Timestamp [UCT]: 2024-04-17 18:04:53 Age [y:d:h:m:s]: 00:157:05:02:30
Block: 1002644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112616 RingCT/type: yes/0
Extra: 01a4676c70f26213d91c81922502b507711b04c2413470f1bf2afa611cf4917c5c02110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec7b512f8b824e41c411ee0b50d045d104588d451b0522a32bba62c6bc2b8ff5 0.600000000000 1463162 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": 1002654, "vin": [ { "gen": { "height": 1002644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec7b512f8b824e41c411ee0b50d045d104588d451b0522a32bba62c6bc2b8ff5" } } ], "extra": [ 1, 164, 103, 108, 112, 242, 98, 19, 217, 28, 129, 146, 37, 2, 181, 7, 113, 27, 4, 194, 65, 52, 112, 241, 191, 42, 250, 97, 28, 244, 145, 124, 92, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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