Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 794a3aecd12d58950df61d0969b5bb5446570a336e5abd87651f81356ef40fe5

Tx prefix hash: 04bfd1a32dfcc287ba179a5df40fb2aac72bcf7ec105de445aef56bec1614c4a
Tx public key: 296f61c3279eec2ba485a8d23e856b96c51c20adf45d472f66dbc2c774e60af1
Timestamp: 1648467293 Timestamp [UCT]: 2022-03-28 11:34:53 Age [y:d:h:m:s]: 02:248:17:35:48
Block: 468156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 697328 RingCT/type: yes/0
Extra: 01296f61c3279eec2ba485a8d23e856b96c51c20adf45d472f66dbc2c774e60af102110000000206faf294000000000000000000

1 output(s) for total of 17.250634888000 dcy

stealth address amount amount idx
00: b5f64f7ee4c48afe534f3b06666410c6b12ba14fdece0ca2cab691d9cd5ca1be 17.250634888000 886810 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": 468166, "vin": [ { "gen": { "height": 468156 } } ], "vout": [ { "amount": 17250634888, "target": { "key": "b5f64f7ee4c48afe534f3b06666410c6b12ba14fdece0ca2cab691d9cd5ca1be" } } ], "extra": [ 1, 41, 111, 97, 195, 39, 158, 236, 43, 164, 133, 168, 210, 62, 133, 107, 150, 197, 28, 32, 173, 244, 93, 71, 47, 102, 219, 194, 199, 116, 230, 10, 241, 2, 17, 0, 0, 0, 2, 6, 250, 242, 148, 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