Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfbf95f55de8ac546d500311f236e8aebd511c2acdaf549d170e8695f89f5c9f

Tx prefix hash: b9eef607a01d0e43f08e1d3e85ad8acc5f156e2d9328516cda01a378dfbcef89
Tx public key: cc734a880b61391b0bea63a4a3bd84d172cae1ad492dab69327cb1dc910be927
Timestamp: 1700290885 Timestamp [UCT]: 2023-11-18 07:01:25 Age [y:d:h:m:s]: 01:059:23:57:14
Block: 894155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304278 RingCT/type: yes/0
Extra: 01cc734a880b61391b0bea63a4a3bd84d172cae1ad492dab69327cb1dc910be92702110000000133af99f4000000000000000000

1 output(s) for total of 0.668795428000 dcy

stealth address amount amount idx
00: b949f29227b1be1311ec68a6ca5f1c15436cbe629aa0b40c0eed933f551a765f 0.668795428000 1350346 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": 894165, "vin": [ { "gen": { "height": 894155 } } ], "vout": [ { "amount": 668795428, "target": { "key": "b949f29227b1be1311ec68a6ca5f1c15436cbe629aa0b40c0eed933f551a765f" } } ], "extra": [ 1, 204, 115, 74, 136, 11, 97, 57, 27, 11, 234, 99, 164, 163, 189, 132, 209, 114, 202, 225, 173, 73, 45, 171, 105, 50, 124, 177, 220, 145, 11, 233, 39, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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