Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7de3262fa63a6fa671c955512d1f8f534ca2f01b270f0aca4628f4580a6ae902

Tx prefix hash: 1ed5124d9762ae66d495ccabe970bb4f396c6137546d95a52526d4dcb1161278
Tx public key: 552dd4f5b22946e6f1e94f683909f2e63e7806fd89d6b1eb59a22556ec3bde78
Timestamp: 1679155110 Timestamp [UCT]: 2023-03-18 15:58:30 Age [y:d:h:m:s]: 02:094:23:53:35
Block: 719824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 589323 RingCT/type: yes/0
Extra: 01552dd4f5b22946e6f1e94f683909f2e63e7806fd89d6b1eb59a22556ec3bde7802110000000375e3f0e9000000000000000000

1 output(s) for total of 2.528856343000 dcy

stealth address amount amount idx
00: 2c9d391f32b9ec636df0ae5c7c97f4f61f76e2a3f924e6c8c8eb2767f4d57764 2.528856343000 1164571 of 0

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": 719834, "vin": [ { "gen": { "height": 719824 } } ], "vout": [ { "amount": 2528856343, "target": { "key": "2c9d391f32b9ec636df0ae5c7c97f4f61f76e2a3f924e6c8c8eb2767f4d57764" } } ], "extra": [ 1, 85, 45, 212, 245, 178, 41, 70, 230, 241, 233, 79, 104, 57, 9, 242, 230, 62, 120, 6, 253, 137, 214, 177, 235, 89, 162, 37, 86, 236, 59, 222, 120, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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