Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ea02a283bc1ca65177ed6f7733d04d8ce44d78c003e32fc5330bb042afbea63

Tx prefix hash: 3e72984797675ce1c34b6eb612e903a7760db6f5e7e6740863c0181df1b3d035
Tx public key: bdc49eea40ccfdc406e158e8425d228185380a4d55fdc84baffb1a8d61343a07
Timestamp: 1750594335 Timestamp [UCT]: 2025-06-22 12:12:15 Age [y:d:h:m:s]: 00:150:19:49:14
Block: 1310425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105683 RingCT/type: yes/0
Extra: 01bdc49eea40ccfdc406e158e8425d228185380a4d55fdc84baffb1a8d61343a07021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9f8ba226d3f0e0ba3dc6a19822b701f045aaa8f1863032ddfbbe15632b90c20 0.600000000000 1798046 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": 1310435, "vin": [ { "gen": { "height": 1310425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9f8ba226d3f0e0ba3dc6a19822b701f045aaa8f1863032ddfbbe15632b90c20" } } ], "extra": [ 1, 189, 196, 158, 234, 64, 204, 253, 196, 6, 225, 88, 232, 66, 93, 34, 129, 133, 56, 10, 77, 85, 253, 200, 75, 175, 251, 26, 141, 97, 52, 58, 7, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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