Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4108619ac9b498c310e6f4065dfa2d2b66f50055cd6a9aa9e241a01b3545091

Tx prefix hash: 74e33bac25c6dcbf74e9990525f651cebb68a80fcfdfde4ab8a1a71ff8747c0c
Tx public key: 957cbaf402b14d417a77e3e95388642cdcca24561e1aa37744f6285dde8c51e0
Timestamp: 1577472833 Timestamp [UCT]: 2019-12-27 18:53:53 Age [y:d:h:m:s]: 05:001:02:01:28
Block: 33028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150804 RingCT/type: yes/0
Extra: 01957cbaf402b14d417a77e3e95388642cdcca24561e1aa37744f6285dde8c51e0021100000001d81c26c0000000000000000000

1 output(s) for total of 477.051629099000 dcy

stealth address amount amount idx
00: 02ed4c3cb63dd9a729376b8757284c84292543fe280437d7d8c0c9ac0f534f4e 477.051629099000 55127 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": 33038, "vin": [ { "gen": { "height": 33028 } } ], "vout": [ { "amount": 477051629099, "target": { "key": "02ed4c3cb63dd9a729376b8757284c84292543fe280437d7d8c0c9ac0f534f4e" } } ], "extra": [ 1, 149, 124, 186, 244, 2, 177, 77, 65, 122, 119, 227, 233, 83, 136, 100, 44, 220, 202, 36, 86, 30, 26, 163, 119, 68, 246, 40, 93, 222, 140, 81, 224, 2, 17, 0, 0, 0, 1, 216, 28, 38, 192, 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