Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f557f19ff2d963ef72dc58469d4f53da2d16f3460c99bd30a9f013228d1e0470

Tx prefix hash: b70866f8ba205a218db8369591bcb2ec91f4d3b2536d8914642e68c39399f68c
Tx public key: d1b5fdc4ab19e4897e14e856576f31bce9648118a1b99fe0e9f33b78d081781b
Timestamp: 1746352585 Timestamp [UCT]: 2025-05-04 09:56:25 Age [y:d:h:m:s]: 00:245:06:17:43
Block: 1275506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173084 RingCT/type: yes/0
Extra: 01d1b5fdc4ab19e4897e14e856576f31bce9648118a1b99fe0e9f33b78d081781b02110000000a9f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d974ff745406e42aacf9ccceb4caa984ca8b61ce44170c62c7a83adfa2d27cd0 0.600000000000 1762819 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": 1275516, "vin": [ { "gen": { "height": 1275506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d974ff745406e42aacf9ccceb4caa984ca8b61ce44170c62c7a83adfa2d27cd0" } } ], "extra": [ 1, 209, 181, 253, 196, 171, 25, 228, 137, 126, 20, 232, 86, 87, 111, 49, 188, 233, 100, 129, 24, 161, 185, 159, 224, 233, 243, 59, 120, 208, 129, 120, 27, 2, 17, 0, 0, 0, 10, 159, 159, 230, 140, 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