Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8af1195cb9fda234af9a60eb5df33eb03003acc40be0c538712889228f56b0a

Tx prefix hash: f58303f39bdb46d2a94d2310059ff046ebcc0f0d5add96eeab15f52d959a2f23
Tx public key: d0aedfb73713afc0379a1937fcdbd1066dc2b76f37da0db775bac566025a058c
Timestamp: 1720312756 Timestamp [UCT]: 2024-07-07 00:39:16 Age [y:d:h:m:s]: 00:262:03:37:29
Block: 1060146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187281 RingCT/type: yes/0
Extra: 01d0aedfb73713afc0379a1937fcdbd1066dc2b76f37da0db775bac566025a058c0211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6f5ebf6293ea9014550ba2dc242207b5e8148a0dedd2bb4c4d06f856c2d4ea8 0.600000000000 1530617 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": 1060156, "vin": [ { "gen": { "height": 1060146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6f5ebf6293ea9014550ba2dc242207b5e8148a0dedd2bb4c4d06f856c2d4ea8" } } ], "extra": [ 1, 208, 174, 223, 183, 55, 19, 175, 192, 55, 154, 25, 55, 252, 219, 209, 6, 109, 194, 183, 111, 55, 218, 13, 183, 117, 186, 197, 102, 2, 90, 5, 140, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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