Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99a9fb7390540b601279a65e1157279d90df3fd41c581f265fb18924f7b9b692

Tx prefix hash: 83851c060ff09b61bef7154d111ff575f44e09580ce2c9d536873eeae2a875f0
Tx public key: a5708f20a4a4d962e3f704f46c64740f3ee24e3c3886483ef407138992360090
Timestamp: 1698575915 Timestamp [UCT]: 2023-10-29 10:38:35 Age [y:d:h:m:s]: 02:026:16:22:30
Block: 880153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538665 RingCT/type: yes/0
Extra: 01a5708f20a4a4d962e3f704f46c64740f3ee24e3c3886483ef407138992360090021100000002faf35c9c000000000000000000

1 output(s) for total of 0.744196725000 dcy

stealth address amount amount idx
00: 55f17001b5a460e0794a678c5881491ce4cc7b01a65a426551bdac729fb343ab 0.744196725000 1335699 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": 880163, "vin": [ { "gen": { "height": 880153 } } ], "vout": [ { "amount": 744196725, "target": { "key": "55f17001b5a460e0794a678c5881491ce4cc7b01a65a426551bdac729fb343ab" } } ], "extra": [ 1, 165, 112, 143, 32, 164, 164, 217, 98, 227, 247, 4, 244, 108, 100, 116, 15, 62, 226, 78, 60, 56, 134, 72, 62, 244, 7, 19, 137, 146, 54, 0, 144, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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