Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 461a31e51f4e67a51507f5a592e0ff810e4663a6f7d80493e1987e28d950d2ea

Tx prefix hash: ad4f29040af5868036abbd13a2ec4e8deca2f3f91f8eb45ba121f60413daffa6
Tx public key: ffefda4c73e84a25d138e1cb0455af1561e625ece477d9b857d4a369866891b2
Timestamp: 1750644324 Timestamp [UCT]: 2025-06-23 02:05:24 Age [y:d:h:m:s]: 00:149:12:03:09
Block: 1310834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104736 RingCT/type: yes/0
Extra: 01ffefda4c73e84a25d138e1cb0455af1561e625ece477d9b857d4a369866891b20211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa819a3c12d74241db90300c3df218ad5150b4ea3cb76aa69b02a623cb7d5a26 0.600000000000 1798457 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": 1310844, "vin": [ { "gen": { "height": 1310834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa819a3c12d74241db90300c3df218ad5150b4ea3cb76aa69b02a623cb7d5a26" } } ], "extra": [ 1, 255, 239, 218, 76, 115, 232, 74, 37, 209, 56, 225, 203, 4, 85, 175, 21, 97, 230, 37, 236, 228, 119, 217, 184, 87, 212, 163, 105, 134, 104, 145, 178, 2, 17, 0, 0, 0, 1, 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