Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 969ebb9e774a1424ee06603085660fe2d8c637f3afa4d4b6df0de7dd9e627a62

Tx prefix hash: a070f6de95ed1c2a56e56bd6dea0e244a993fd7438fe2e54b25b9b36faf4b684
Tx public key: 20a9e38ca8eed34e6a3f1c262fbd5c98ff959df79b0fd02018395a2b1e0f6040
Timestamp: 1710058834 Timestamp [UCT]: 2024-03-10 08:20:34 Age [y:d:h:m:s]: 01:029:05:02:15
Block: 975149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281851 RingCT/type: yes/0
Extra: 0120a9e38ca8eed34e6a3f1c262fbd5c98ff959df79b0fd02018395a2b1e0f6040021100000002b757f2ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 695377c9ef11067aa7fc6b9abe15c95391055f75b84a1f73f759c37f308714b7 0.600000000000 1435120 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": 975159, "vin": [ { "gen": { "height": 975149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "695377c9ef11067aa7fc6b9abe15c95391055f75b84a1f73f759c37f308714b7" } } ], "extra": [ 1, 32, 169, 227, 140, 168, 238, 211, 78, 106, 63, 28, 38, 47, 189, 92, 152, 255, 149, 157, 247, 155, 15, 208, 32, 24, 57, 90, 43, 30, 15, 96, 64, 2, 17, 0, 0, 0, 2, 183, 87, 242, 172, 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