Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a88bbab2300e4d2c17f2c4136c37be3693b524952f3f41afebbf6f0863e462b1

Tx prefix hash: f1a015b2f0744e12bd3163a26ed839096e9df6d15bb1d0c5d79d89d471dcbcaa
Tx public key: 954f177a27f8de4e747ac112ff3debd2f050e9105dcb72d9312769c144604154
Timestamp: 1583054087 Timestamp [UCT]: 2020-03-01 09:14:47 Age [y:d:h:m:s]: 05:058:22:33:49
Block: 74440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196710 RingCT/type: yes/0
Extra: 01954f177a27f8de4e747ac112ff3debd2f050e9105dcb72d9312769c144604154021100000344026b59f3000000000000000000

1 output(s) for total of 347.822506805000 dcy

stealth address amount amount idx
00: 57e876ed5b0e1c02e46d5c8506ef8cf1767f07b0be74606c3ec94dcaf03ddbf0 347.822506805000 137761 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": 74450, "vin": [ { "gen": { "height": 74440 } } ], "vout": [ { "amount": 347822506805, "target": { "key": "57e876ed5b0e1c02e46d5c8506ef8cf1767f07b0be74606c3ec94dcaf03ddbf0" } } ], "extra": [ 1, 149, 79, 23, 122, 39, 248, 222, 78, 116, 122, 193, 18, 255, 61, 235, 210, 240, 80, 233, 16, 93, 203, 114, 217, 49, 39, 105, 193, 68, 96, 65, 84, 2, 17, 0, 0, 3, 68, 2, 107, 89, 243, 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