Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6447587226f5cf1f7e5f2bef148cfbb5ec1848b7acb241d1eeac2a105d2ce1b3

Tx prefix hash: f76d41803718464a69200ffff5c7b62183b1bd13ddb30557e2834371cd07fc5d
Tx public key: a242bf8ca7c60bcd33745199a7c528ebb14f08e27c93822c0ae241e5959a4f11
Timestamp: 1749916641 Timestamp [UCT]: 2025-06-14 15:57:21 Age [y:d:h:m:s]: 00:159:16:50:24
Block: 1304947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111881 RingCT/type: yes/0
Extra: 01a242bf8ca7c60bcd33745199a7c528ebb14f08e27c93822c0ae241e5959a4f1102110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18a91f917e6cb27a87a5d3cd5878ffbe0504b1f47faab5136ee537307dbd4e80 0.600000000000 1792542 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": 1304957, "vin": [ { "gen": { "height": 1304947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18a91f917e6cb27a87a5d3cd5878ffbe0504b1f47faab5136ee537307dbd4e80" } } ], "extra": [ 1, 162, 66, 191, 140, 167, 198, 11, 205, 51, 116, 81, 153, 167, 197, 40, 235, 177, 79, 8, 226, 124, 147, 130, 44, 10, 226, 65, 229, 149, 154, 79, 17, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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