Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35f6f0fd7e1600afa6de35bbb9dc5b548f95b144ae4fd4673765bb8df6ac0540

Tx prefix hash: fcfb310eaee7caaa08aa1c81aca86134d0bfbe12a53ca6e7c4084ebb6f134208
Tx public key: 8226f479f7d71169eb9c28e2b598793d0fa357c78740c5c5c641584cd06b5d23
Timestamp: 1746188991 Timestamp [UCT]: 2025-05-02 12:29:51 Age [y:d:h:m:s]: 00:192:12:45:02
Block: 1274150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135307 RingCT/type: yes/0
Extra: 018226f479f7d71169eb9c28e2b598793d0fa357c78740c5c5c641584cd06b5d230211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd08b56e517a0d76f378b331d55f0b82ff4a97f32c467f0935dea7f05c8c9805 0.600000000000 1761441 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": 1274160, "vin": [ { "gen": { "height": 1274150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd08b56e517a0d76f378b331d55f0b82ff4a97f32c467f0935dea7f05c8c9805" } } ], "extra": [ 1, 130, 38, 244, 121, 247, 215, 17, 105, 235, 156, 40, 226, 181, 152, 121, 61, 15, 163, 87, 199, 135, 64, 197, 197, 198, 65, 88, 76, 208, 107, 93, 35, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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