Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbe7f8cbfcf2d1539cbb0624a0addaf50ba674670ff46f74f7e6284ebaf0da3e

Tx prefix hash: fc730d6227b849e21f14dcdc1df5cb2131753be69c0315f33d0245322b2d2802
Tx public key: d9414126094aa8a5c130e2e3ebdcbe0d5454b69c6e3f5a058aa97e3a22ac2cbf
Timestamp: 1737533319 Timestamp [UCT]: 2025-01-22 08:08:39 Age [y:d:h:m:s]: 00:150:22:05:35
Block: 1202725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107536 RingCT/type: yes/0
Extra: 01d9414126094aa8a5c130e2e3ebdcbe0d5454b69c6e3f5a058aa97e3a22ac2cbf0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0afe7dcf53a6126b252c4d6f3322a601d5239f6582d471216f5c270f70889f8f 0.600000000000 1689390 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": 1202735, "vin": [ { "gen": { "height": 1202725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0afe7dcf53a6126b252c4d6f3322a601d5239f6582d471216f5c270f70889f8f" } } ], "extra": [ 1, 217, 65, 65, 38, 9, 74, 168, 165, 193, 48, 226, 227, 235, 220, 190, 13, 84, 84, 182, 156, 110, 63, 90, 5, 138, 169, 126, 58, 34, 172, 44, 191, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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