Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3994f1ad070b3e909183e4d77c52994563ffcce6cd15c9da7268ce86d3fb1ad6

Tx prefix hash: 05af6012a75dff3d1b791ac4158b02d90a6ab72c510b3821f792529595d3d0f8
Tx public key: fecbf960aae0c233515a4df1ef74e2952e4736a16fcb8bf376f5f459c341e100
Timestamp: 1722268262 Timestamp [UCT]: 2024-07-29 15:51:02 Age [y:d:h:m:s]: 00:254:20:23:27
Block: 1076355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182057 RingCT/type: yes/0
Extra: 01fecbf960aae0c233515a4df1ef74e2952e4736a16fcb8bf376f5f459c341e10002110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 316d7015156381f416a316356d4a1d2319a3b2eda7b15e4b837d928b689126c1 0.600000000000 1548892 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": 1076365, "vin": [ { "gen": { "height": 1076355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "316d7015156381f416a316356d4a1d2319a3b2eda7b15e4b837d928b689126c1" } } ], "extra": [ 1, 254, 203, 249, 96, 170, 224, 194, 51, 81, 90, 77, 241, 239, 116, 226, 149, 46, 71, 54, 161, 111, 203, 139, 243, 118, 245, 244, 89, 195, 65, 225, 0, 2, 17, 0, 0, 0, 8, 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