Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f7b3e04674618c2a4237892e4c8fa9b5ca381bd621c4d60646098ecd480753b

Tx prefix hash: 4b830f5d3e164ccbd84a136f19bcfe0a8cbca526b3ea63ab0a073ee549397add
Tx public key: 2904279fd9a15669477a4e898facc9a9e84c671cb7f5348a3f7eb8d0b703482d
Timestamp: 1755928733 Timestamp [UCT]: 2025-08-23 05:58:53 Age [y:d:h:m:s]: 00:087:17:15:44
Block: 1352496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62630 RingCT/type: yes/0
Extra: 012904279fd9a15669477a4e898facc9a9e84c671cb7f5348a3f7eb8d0b703482d0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46890ebe0422b91581c780ad034711935ba0e1a2984adab0c9330c8ca7d30ade 0.600000000000 1840461 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": 1352506, "vin": [ { "gen": { "height": 1352496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46890ebe0422b91581c780ad034711935ba0e1a2984adab0c9330c8ca7d30ade" } } ], "extra": [ 1, 41, 4, 39, 159, 217, 161, 86, 105, 71, 122, 78, 137, 143, 172, 201, 169, 232, 76, 103, 28, 183, 245, 52, 138, 63, 126, 184, 208, 183, 3, 72, 45, 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