Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dd90e78a59c01f75c592336bfdb2684adb565d0f60b25d0bbcc54f0b82c0b67

Tx prefix hash: 2dc2e1105a0877d287eadc7dc8dcf2cad9469a1ca38dde6cf0214c1187de866d
Tx public key: bfae66591e4fd8bcc81859ded18b587364c7019b9143c28cb3ba059d00aab75b
Timestamp: 1754929306 Timestamp [UCT]: 2025-08-11 16:21:46 Age [y:d:h:m:s]: 00:106:23:34:40
Block: 1344928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75717 RingCT/type: yes/0
Extra: 01bfae66591e4fd8bcc81859ded18b587364c7019b9143c28cb3ba059d00aab75b021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20fbaf4673fd5c71cc4a97474b9bcf6aa7177f95d24d0a266bd6a44215b94a7b 0.600000000000 1832815 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": 1344938, "vin": [ { "gen": { "height": 1344928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20fbaf4673fd5c71cc4a97474b9bcf6aa7177f95d24d0a266bd6a44215b94a7b" } } ], "extra": [ 1, 191, 174, 102, 89, 30, 79, 216, 188, 200, 24, 89, 222, 209, 139, 88, 115, 100, 199, 1, 155, 145, 67, 194, 140, 179, 186, 5, 157, 0, 170, 183, 91, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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