Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dc63be8e8ca86d6c14968163de9c25ffeeeb807b38a702fda17b38ef23fedb4

Tx prefix hash: 9fb7b4dbde41f92292e97b431c17c2610ac41c394556d0a6780003159d938a56
Tx public key: f35da8f8ef5fd4d5e5e9b8286e5517b67b8f143a5892ffdefd3a5418bf81270a
Timestamp: 1745379987 Timestamp [UCT]: 2025-04-23 03:46:27 Age [y:d:h:m:s]: 00:212:14:04:09
Block: 1267448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149657 RingCT/type: yes/0
Extra: 01f35da8f8ef5fd4d5e5e9b8286e5517b67b8f143a5892ffdefd3a5418bf81270a021100000008dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5b36429f3fbad110cd9b80e504a9314ea803458ae79185dd18f744a676c5431 0.600000000000 1754677 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": 1267458, "vin": [ { "gen": { "height": 1267448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5b36429f3fbad110cd9b80e504a9314ea803458ae79185dd18f744a676c5431" } } ], "extra": [ 1, 243, 93, 168, 248, 239, 95, 212, 213, 229, 233, 184, 40, 110, 85, 23, 182, 123, 143, 20, 58, 88, 146, 255, 222, 253, 58, 84, 24, 191, 129, 39, 10, 2, 17, 0, 0, 0, 8, 219, 181, 113, 193, 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