Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08984c60654fa2bc65598869f85a90cae331ec626b214ffd7a4745743f8b5ca2

Tx prefix hash: cdc096e49dbffbed288fc5ba2ecccb1167bd920274b99361b9e29f1ba5bef9b1
Tx public key: b51a087773b7c47c165057f0bd0c01507810588e5617a9ae401a5da074d456f3
Timestamp: 1576474976 Timestamp [UCT]: 2019-12-16 05:42:56 Age [y:d:h:m:s]: 05:051:05:23:30
Block: 27895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1183266 RingCT/type: yes/0
Extra: 01b51a087773b7c47c165057f0bd0c01507810588e5617a9ae401a5da074d456f3021100000017d81c26c0000000000000000000

1 output(s) for total of 496.130171960000 dcy

stealth address amount amount idx
00: 0b8e5f7b6b1aa3bef0d3a733b8ce10df691b0d90971d6679d8ca6509d58c7776 496.130171960000 46081 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": 27905, "vin": [ { "gen": { "height": 27895 } } ], "vout": [ { "amount": 496130171960, "target": { "key": "0b8e5f7b6b1aa3bef0d3a733b8ce10df691b0d90971d6679d8ca6509d58c7776" } } ], "extra": [ 1, 181, 26, 8, 119, 115, 183, 196, 124, 22, 80, 87, 240, 189, 12, 1, 80, 120, 16, 88, 142, 86, 23, 169, 174, 64, 26, 93, 160, 116, 212, 86, 243, 2, 17, 0, 0, 0, 23, 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