Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7ba6864ae4d52ccb48f9b4a110841753e7c7f74a009c099e85f187eeb7ed5a7

Tx prefix hash: c62cfb9fcadc0c5da7830fb4076f72be090a7e1dc752c1473417bf9be668488f
Tx public key: 9b89e93bce308b95aee323b2d4300d0c7fedc3d608f27c830cd5e726eede7f59
Timestamp: 1696769642 Timestamp [UCT]: 2023-10-08 12:54:02 Age [y:d:h:m:s]: 01:164:04:25:43
Block: 865175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378386 RingCT/type: yes/0
Extra: 019b89e93bce308b95aee323b2d4300d0c7fedc3d608f27c830cd5e726eede7f5902110000000433af99f4000000000000000000

1 output(s) for total of 0.834288214000 dcy

stealth address amount amount idx
00: 8f3357fd08c33c09ad5ebb98dfc676df10e34e842fd7870fd020f0bb1fd46b5f 0.834288214000 1319701 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": 865185, "vin": [ { "gen": { "height": 865175 } } ], "vout": [ { "amount": 834288214, "target": { "key": "8f3357fd08c33c09ad5ebb98dfc676df10e34e842fd7870fd020f0bb1fd46b5f" } } ], "extra": [ 1, 155, 137, 233, 59, 206, 48, 139, 149, 174, 227, 35, 178, 212, 48, 13, 12, 127, 237, 195, 214, 8, 242, 124, 131, 12, 213, 231, 38, 238, 222, 127, 89, 2, 17, 0, 0, 0, 4, 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