Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ea3712348377e6ed0aa8ee4afa150c3c1cd536d1442b2eddf76ea4b97a0326f

Tx prefix hash: 1ba33d83b252fb2e972f7d1e8d07f4e132e4976ad94d1f2cb046f62d00e021f8
Tx public key: 16a3f3b6ad8d97a3d551d161127b3d91ec82f0c91de74555549cf42e4701f54b
Timestamp: 1745690991 Timestamp [UCT]: 2025-04-26 18:09:51 Age [y:d:h:m:s]: 00:010:23:25:40
Block: 1270041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7835 RingCT/type: yes/0
Extra: 0116a3f3b6ad8d97a3d551d161127b3d91ec82f0c91de74555549cf42e4701f54b02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2060a02b64eebd9d3e4ce52061a47e7be5fa2036999295688422f8766d80d790 0.600000000000 1757282 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": 1270051, "vin": [ { "gen": { "height": 1270041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2060a02b64eebd9d3e4ce52061a47e7be5fa2036999295688422f8766d80d790" } } ], "extra": [ 1, 22, 163, 243, 182, 173, 141, 151, 163, 213, 81, 209, 97, 18, 123, 61, 145, 236, 130, 240, 201, 29, 231, 69, 85, 84, 156, 244, 46, 71, 1, 245, 75, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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