Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 284f7ebd84723a78b926fb7267c385c68ae44ebb12a29b0cc50ba17bf582db29

Tx prefix hash: fa68e923e05c0004512a13e8a14daff40dae04b9db2bf9ae26e49a82b4a3d3b8
Tx public key: fc7ea8e5b12749c2effb66ef563f734726d0eca1a380f37e3a8d133044a9b407
Timestamp: 1761163914 Timestamp [UCT]: 2025-10-22 20:11:54 Age [y:d:h:m:s]: 00:036:13:18:30
Block: 1395716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26167 RingCT/type: yes/0
Extra: 01fc7ea8e5b12749c2effb66ef563f734726d0eca1a380f37e3a8d133044a9b40702110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60fe6dd4ce53b8e0aee31ee3583ab1e1d9963eeb43b9039358305e048d45ab66 0.600000000000 1883999 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": 1395726, "vin": [ { "gen": { "height": 1395716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60fe6dd4ce53b8e0aee31ee3583ab1e1d9963eeb43b9039358305e048d45ab66" } } ], "extra": [ 1, 252, 126, 168, 229, 177, 39, 73, 194, 239, 251, 102, 239, 86, 63, 115, 71, 38, 208, 236, 161, 163, 128, 243, 126, 58, 141, 19, 48, 68, 169, 180, 7, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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