Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 827d7429dd27a160d2dcc5d377f664b0f60edbd68d3be461b44e1698b4cb0937

Tx prefix hash: 9d1e08f6a3bf4d0000465f56698ebd2a35f1e4beaec0d3a41278957959015dca
Tx public key: 2b6b15886e12da0d992eaee48ecc1d485962c3f8aba87c67c398916b986a044c
Timestamp: 1577874744 Timestamp [UCT]: 2020-01-01 10:32:24 Age [y:d:h:m:s]: 05:304:14:42:48
Block: 36277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1365322 RingCT/type: yes/0
Extra: 012b6b15886e12da0d992eaee48ecc1d485962c3f8aba87c67c398916b986a044c0211000000094ac5aa02000000000000000000

1 output(s) for total of 465.371831994000 dcy

stealth address amount amount idx
00: 11440fad74159e3bd5d7d0b525cc836f8479a0443ebe92666ef6841472228a8b 465.371831994000 61409 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": 36287, "vin": [ { "gen": { "height": 36277 } } ], "vout": [ { "amount": 465371831994, "target": { "key": "11440fad74159e3bd5d7d0b525cc836f8479a0443ebe92666ef6841472228a8b" } } ], "extra": [ 1, 43, 107, 21, 136, 110, 18, 218, 13, 153, 46, 174, 228, 142, 204, 29, 72, 89, 98, 195, 248, 171, 168, 124, 103, 195, 152, 145, 107, 152, 106, 4, 76, 2, 17, 0, 0, 0, 9, 74, 197, 170, 2, 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