Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04d916eeaa75e12a2e432d3f6e7de8ee63716415606d2ce827cd2dc7bfc69337

Tx prefix hash: 0e1575a0ff046405248cc70dbcfe36d5fe7ba4636209c9d7b4c1e3747ab871a3
Tx public key: 94e08952056e48043e2ee092d37ec1a648eafb4e4df569753882e83558e1e90c
Timestamp: 1737250240 Timestamp [UCT]: 2025-01-19 01:30:40 Age [y:d:h:m:s]: 00:056:21:06:50
Block: 1200387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40465 RingCT/type: yes/0
Extra: 0194e08952056e48043e2ee092d37ec1a648eafb4e4df569753882e83558e1e90c021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c94e3c5bcbf2cb91b5a4036f3e4aadb122eee80931ec59131246777bfed5b8e9 0.600000000000 1687030 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": 1200397, "vin": [ { "gen": { "height": 1200387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c94e3c5bcbf2cb91b5a4036f3e4aadb122eee80931ec59131246777bfed5b8e9" } } ], "extra": [ 1, 148, 224, 137, 82, 5, 110, 72, 4, 62, 46, 224, 146, 211, 126, 193, 166, 72, 234, 251, 78, 77, 245, 105, 117, 56, 130, 232, 53, 88, 225, 233, 12, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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