Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa2c9e6d0945c170ba6990cfea095790dabe8a709a032f757cc22701d179b0a0

Tx prefix hash: 1270d211e3dd2dac01d6c1abdefa9b62f2beda54a8dd232c586bea78f556db45
Tx public key: 917aab9e322f18ec5bf1b10fe7341d821c0edff1ee01692ba7b2c26db92e6956
Timestamp: 1750700097 Timestamp [UCT]: 2025-06-23 17:34:57 Age [y:d:h:m:s]: 00:144:06:33:34
Block: 1311272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101021 RingCT/type: yes/0
Extra: 01917aab9e322f18ec5bf1b10fe7341d821c0edff1ee01692ba7b2c26db92e6956021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1ad9cbdab5c2df0b0493c7e106b88fc76879a19f3a78f7ce6ef6730d310a9b2 0.600000000000 1798897 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": 1311282, "vin": [ { "gen": { "height": 1311272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1ad9cbdab5c2df0b0493c7e106b88fc76879a19f3a78f7ce6ef6730d310a9b2" } } ], "extra": [ 1, 145, 122, 171, 158, 50, 47, 24, 236, 91, 241, 177, 15, 231, 52, 29, 130, 28, 14, 223, 241, 238, 1, 105, 43, 167, 178, 194, 109, 185, 46, 105, 86, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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