Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26a335fc1715b38eae809f58096aba8e10fad43f4c12c92e0bb60ded7ae510e6

Tx prefix hash: eef58aba2c8a46343dbdfe2c21ba64a6a9a8bdba39d2c153a6fe8a685e3118b3
Tx public key: 8d29b312ac6991896305828f27d62e643e0e4af15dd2dd98082077f23089a192
Timestamp: 1762795167 Timestamp [UCT]: 2025-11-10 17:19:27 Age [y:d:h:m:s]: 00:011:07:07:14
Block: 1409221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8086 RingCT/type: yes/0
Extra: 018d29b312ac6991896305828f27d62e643e0e4af15dd2dd98082077f23089a1920211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dfb2e273e7bbb5b6ba5b3bb7790ff03756dedca9e6b1d88f8f92942f3f09408 0.600000000000 1897656 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": 1409231, "vin": [ { "gen": { "height": 1409221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dfb2e273e7bbb5b6ba5b3bb7790ff03756dedca9e6b1d88f8f92942f3f09408" } } ], "extra": [ 1, 141, 41, 179, 18, 172, 105, 145, 137, 99, 5, 130, 143, 39, 214, 46, 100, 62, 14, 74, 241, 93, 210, 221, 152, 8, 32, 119, 242, 48, 137, 161, 146, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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