Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e68919132411736c292271e552a2e06a5cedf1a409b9c562e4e0855c19785b39

Tx prefix hash: 26fa36218c8a8e70e6131ef156f1ad08ea2e8f10b1fa516a58e52b2bbca61898
Tx public key: e897ea061f2da4fe0a02da3a02833c8ad5d2059653663e63da56fffbe017d9fe
Timestamp: 1708695596 Timestamp [UCT]: 2024-02-23 13:39:56 Age [y:d:h:m:s]: 01:053:08:55:56
Block: 963836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299166 RingCT/type: yes/0
Extra: 01e897ea061f2da4fe0a02da3a02833c8ad5d2059653663e63da56fffbe017d9fe02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6781f0953aa6446350f668c08f1204d1542af2f526754c4f5bfd2792a4fa93e5 0.600000000000 1423563 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": 963846, "vin": [ { "gen": { "height": 963836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6781f0953aa6446350f668c08f1204d1542af2f526754c4f5bfd2792a4fa93e5" } } ], "extra": [ 1, 232, 151, 234, 6, 31, 45, 164, 254, 10, 2, 218, 58, 2, 131, 60, 138, 213, 210, 5, 150, 83, 102, 62, 99, 218, 86, 255, 251, 224, 23, 217, 254, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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