Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fc2ecb1cf0acf3ac9af861f76626f2bb27665d4c6d80c6eefe34cac64ead89c

Tx prefix hash: 48b942af423c48739f4d6c7f42e0d2d725d504993a0f238400fb52a121078dcc
Tx public key: 2644b7791100b140b449c69cddff48171164559b647e07e3cb24ae9dc4a9ae71
Timestamp: 1760373443 Timestamp [UCT]: 2025-10-13 16:37:23 Age [y:d:h:m:s]: 00:040:10:44:15
Block: 1389164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28952 RingCT/type: yes/0
Extra: 012644b7791100b140b449c69cddff48171164559b647e07e3cb24ae9dc4a9ae710211000000035dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0a3cd6a8e6ad9275f2867d8d991cea03e4733964a3b1fc0e78b8df82ebe8720 0.600000000000 1877393 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": 1389174, "vin": [ { "gen": { "height": 1389164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0a3cd6a8e6ad9275f2867d8d991cea03e4733964a3b1fc0e78b8df82ebe8720" } } ], "extra": [ 1, 38, 68, 183, 121, 17, 0, 177, 64, 180, 73, 198, 156, 221, 255, 72, 23, 17, 100, 85, 155, 100, 126, 7, 227, 203, 36, 174, 157, 196, 169, 174, 113, 2, 17, 0, 0, 0, 3, 93, 251, 190, 42, 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