Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2438ea24b31ca5256c171bed2ffc6f58e31da4e7bb8a56ae41ef73b9bcb522b7

Tx prefix hash: 7db8e55be4831fe1f3458decd4dd6d6a1313ba59ce61633030a1368a1022eb15
Tx public key: ffa755bbb6e185f85fe655acae19ac6aa6a4a74a3d273bc0bf2b6be93c5a44ed
Timestamp: 1720389565 Timestamp [UCT]: 2024-07-07 21:59:25 Age [y:d:h:m:s]: 00:311:05:38:43
Block: 1060790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222393 RingCT/type: yes/0
Extra: 01ffa755bbb6e185f85fe655acae19ac6aa6a4a74a3d273bc0bf2b6be93c5a44ed02110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e93530447392e7d6e11d5024b4f93961def9927e4894cbe06dc5c5662497b0a0 0.600000000000 1531277 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": 1060800, "vin": [ { "gen": { "height": 1060790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e93530447392e7d6e11d5024b4f93961def9927e4894cbe06dc5c5662497b0a0" } } ], "extra": [ 1, 255, 167, 85, 187, 182, 225, 133, 248, 95, 230, 85, 172, 174, 25, 172, 106, 166, 164, 167, 74, 61, 39, 59, 192, 191, 43, 107, 233, 60, 90, 68, 237, 2, 17, 0, 0, 0, 12, 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