Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ff5286122ac574447f4d463fad72b79ffd6ec4a0c390d1ebe66f8429d987fe2

Tx prefix hash: 998c90e02dc784a4d7ddd492e6b515959e5080ad9d17330e6e84f02a4422e1fd
Tx public key: bacb09b5a66b7ee79d811b404628fd3e5253f77f33c03248f1c81ca67906e296
Timestamp: 1726124238 Timestamp [UCT]: 2024-09-12 06:57:18 Age [y:d:h:m:s]: 00:101:11:20:36
Block: 1108320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72603 RingCT/type: yes/0
Extra: 01bacb09b5a66b7ee79d811b404628fd3e5253f77f33c03248f1c81ca67906e29602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c975445e771e8cce054fa8c776c7bf068eb0f12f90f5c7a74fe3d8925dddeb0 0.600000000000 1586175 of 15

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": 1108330, "vin": [ { "gen": { "height": 1108320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c975445e771e8cce054fa8c776c7bf068eb0f12f90f5c7a74fe3d8925dddeb0" } } ], "extra": [ 1, 186, 203, 9, 181, 166, 107, 126, 231, 157, 129, 27, 64, 70, 40, 253, 62, 82, 83, 247, 127, 51, 192, 50, 72, 241, 200, 28, 166, 121, 6, 226, 150, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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