Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0de3028bb8d46534e4e1dcbc7a2a95c22abd66ce29ff68ee3c3f72a591d0d8bb

Tx prefix hash: 547763302b1e184e8717c28d5d189f522ab410209dc512f6daa68e02c22c9611
Tx public key: f5c7e80f4033f2598dcc10ae738d3d1beebfb9e877a2ff83188dc53d0a001a1e
Timestamp: 1760840587 Timestamp [UCT]: 2025-10-19 02:23:07 Age [y:d:h:m:s]: 00:093:20:47:57
Block: 1393033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67063 RingCT/type: yes/0
Extra: 01f5c7e80f4033f2598dcc10ae738d3d1beebfb9e877a2ff83188dc53d0a001a1e0211000000052609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a237a76c1545b41f3d45d0a5da58058271d5bf8836ae92f7634717d8bf2207e 0.600000000000 1881290 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": 1393043, "vin": [ { "gen": { "height": 1393033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a237a76c1545b41f3d45d0a5da58058271d5bf8836ae92f7634717d8bf2207e" } } ], "extra": [ 1, 245, 199, 232, 15, 64, 51, 242, 89, 141, 204, 16, 174, 115, 141, 61, 27, 238, 191, 185, 232, 119, 162, 255, 131, 24, 141, 197, 61, 10, 0, 26, 30, 2, 17, 0, 0, 0, 5, 38, 9, 179, 160, 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