Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 929d0cd119cf5bef2b7d27b5b8dc63fba44f51ac486a3d7018f9dd404757f1ab

Tx prefix hash: cc3e281c9eeb1d84bfecb26c5a4b8cb03000043f1ed2e37c8fab6c8f93f324a0
Tx public key: 725ae725f964f9b136c3c8039847c5fadc5b317f431f7c6368de1f8bf6a09454
Timestamp: 1723662777 Timestamp [UCT]: 2024-08-14 19:12:57 Age [y:d:h:m:s]: 01:087:23:10:42
Block: 1087927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321328 RingCT/type: yes/0
Extra: 01725ae725f964f9b136c3c8039847c5fadc5b317f431f7c6368de1f8bf6a0945402110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ef0ca3a74dbfd67cede2251b5a77ba6d734fc4dfac49ac3a527580749e1ff43 0.600000000000 1562538 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": 1087937, "vin": [ { "gen": { "height": 1087927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ef0ca3a74dbfd67cede2251b5a77ba6d734fc4dfac49ac3a527580749e1ff43" } } ], "extra": [ 1, 114, 90, 231, 37, 249, 100, 249, 177, 54, 195, 200, 3, 152, 71, 197, 250, 220, 91, 49, 127, 67, 31, 124, 99, 104, 222, 31, 139, 246, 160, 148, 84, 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