Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f5a07d20a61a39fbc5df31524837411bfa519dd50f4494dd3883616d457c62b

Tx prefix hash: e5a4a365089feabebd3135b92ca85efd9a512fb52e9357ba47e90a016a4cceb0
Tx public key: 11a545f32d0de98255d8d32c2a1fa67ded46ed92a4db7f93b4b2cac8aadf65ea
Timestamp: 1744717201 Timestamp [UCT]: 2025-04-15 11:40:01 Age [y:d:h:m:s]: 00:213:13:06:41
Block: 1261962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150350 RingCT/type: yes/0
Extra: 0111a545f32d0de98255d8d32c2a1fa67ded46ed92a4db7f93b4b2cac8aadf65ea0211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cbfb1b59e08cd4ee0966ef9b054e4548a29b140bc50496a56712b699e7e1ec1 0.600000000000 1749137 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": 1261972, "vin": [ { "gen": { "height": 1261962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cbfb1b59e08cd4ee0966ef9b054e4548a29b140bc50496a56712b699e7e1ec1" } } ], "extra": [ 1, 17, 165, 69, 243, 45, 13, 233, 130, 85, 216, 211, 44, 42, 31, 166, 125, 237, 70, 237, 146, 164, 219, 127, 147, 180, 178, 202, 200, 170, 223, 101, 234, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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