Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b648b24fae16da545cd48f5884c6d8eebc5974eb936edeb702c2e242f6898d2

Tx prefix hash: 279d5a672a697ea56a8dc99f7b342aa6362778dbee923b8e141b6793df827757
Tx public key: b7ad1ea499f8c8d6fcd827da69d05308f9de22da4c41104e71fbb1d6ace35e8d
Timestamp: 1576453878 Timestamp [UCT]: 2019-12-15 23:51:18 Age [y:d:h:m:s]: 05:054:04:22:11
Block: 27877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1185231 RingCT/type: yes/0
Extra: 01b7ad1ea499f8c8d6fcd827da69d05308f9de22da4c41104e71fbb1d6ace35e8d021100000026ad433a0b000000000000000000

1 output(s) for total of 496.181166481000 dcy

stealth address amount amount idx
00: b29d8cc9fb56cb2c425d332eb2331302c996515d5428d288de0af7ede2a5ee5a 496.181166481000 46043 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": 27887, "vin": [ { "gen": { "height": 27877 } } ], "vout": [ { "amount": 496181166481, "target": { "key": "b29d8cc9fb56cb2c425d332eb2331302c996515d5428d288de0af7ede2a5ee5a" } } ], "extra": [ 1, 183, 173, 30, 164, 153, 248, 200, 214, 252, 216, 39, 218, 105, 208, 83, 8, 249, 222, 34, 218, 76, 65, 16, 78, 113, 251, 177, 214, 172, 227, 94, 141, 2, 17, 0, 0, 0, 38, 173, 67, 58, 11, 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