Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd7c1c5fa13675ca45b0423e58eedb20fd1f771f04da01e2b1d3ddb4bbff6fc9

Tx prefix hash: 4fb1fb99887cc1c4b1fb31a301900225583ae1920c7aa30c97517a4f1bc80795
Tx public key: e1374a46ffce3494d5f60c156ae742077ab158f5fb45b7a19c82943be9e4edf8
Timestamp: 1756398188 Timestamp [UCT]: 2025-08-28 16:23:08 Age [y:d:h:m:s]: 00:146:06:32:51
Block: 1356393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104410 RingCT/type: yes/0
Extra: 01e1374a46ffce3494d5f60c156ae742077ab158f5fb45b7a19c82943be9e4edf80211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5f57bdc230a06205454bbd26709a97bfb20312505b0b0511e729d2340279721 0.600000000000 1844402 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": 1356403, "vin": [ { "gen": { "height": 1356393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5f57bdc230a06205454bbd26709a97bfb20312505b0b0511e729d2340279721" } } ], "extra": [ 1, 225, 55, 74, 70, 255, 206, 52, 148, 213, 246, 12, 21, 106, 231, 66, 7, 122, 177, 88, 245, 251, 69, 183, 161, 156, 130, 148, 59, 233, 228, 237, 248, 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