Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb1eebb6a8ddd10ed867239a7e06b80428f59aacd8899ec348567ed72dd4160d

Tx prefix hash: e2b6bc5d309df1f3dd50414c35d65517b44b39b3f4683e535601de9fe88873a5
Tx public key: cce866d49bf8b7be18c9f864a465117dd3c85045c997cc80d7e8147e8d51b7e1
Timestamp: 1694491551 Timestamp [UCT]: 2023-09-12 04:05:51 Age [y:d:h:m:s]: 01:066:00:35:55
Block: 846256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308484 RingCT/type: yes/0
Extra: 01cce866d49bf8b7be18c9f864a465117dd3c85045c997cc80d7e8147e8d51b7e1021100000008faf35c9c000000000000000000

1 output(s) for total of 0.963864875000 dcy

stealth address amount amount idx
00: 29ac15717a6c4e11489b96f22258bbb3ae3eb9563fc4ad0cd1da3b92762ef2ae 0.963864875000 1299704 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": 846266, "vin": [ { "gen": { "height": 846256 } } ], "vout": [ { "amount": 963864875, "target": { "key": "29ac15717a6c4e11489b96f22258bbb3ae3eb9563fc4ad0cd1da3b92762ef2ae" } } ], "extra": [ 1, 204, 232, 102, 212, 155, 248, 183, 190, 24, 201, 248, 100, 164, 101, 17, 125, 211, 200, 80, 69, 201, 151, 204, 128, 215, 232, 20, 126, 141, 81, 183, 225, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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