Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b8e40e36439191297c0730aab10238cc4c3f8be24eae135177f85d22c507fbc

Tx prefix hash: 03c146cd5d796b023f4f0e4a3d1d91515387ff4e2c727e80e15c7d27c616835b
Tx public key: dad5b051e015dc7fac26a1d5f835280db9f95d0a71a8a05fe5384cecec223818
Timestamp: 1757464411 Timestamp [UCT]: 2025-09-10 00:33:31 Age [y:d:h:m:s]: 00:078:09:45:40
Block: 1365078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56110 RingCT/type: yes/0
Extra: 01dad5b051e015dc7fac26a1d5f835280db9f95d0a71a8a05fe5384cecec223818021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04ace2a5f8bcee62b32c18553e5ab7ff0e08464c3166709574203c2d48874301 0.600000000000 1853117 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": 1365088, "vin": [ { "gen": { "height": 1365078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04ace2a5f8bcee62b32c18553e5ab7ff0e08464c3166709574203c2d48874301" } } ], "extra": [ 1, 218, 213, 176, 81, 224, 21, 220, 127, 172, 38, 161, 213, 248, 53, 40, 13, 185, 249, 93, 10, 113, 168, 160, 95, 229, 56, 76, 236, 236, 34, 56, 24, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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