Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1e75042e389041187a6764f3a6f3cbda07c8b891e0e5e1780b6ccf4c3b3a100

Tx prefix hash: 103e6d4b6ba66fba1bbf750a559deef7fedc8cb621d6aa81917c92b16b0f89fe
Tx public key: 12dc19c39481c2ce40daaef6c3d5a323e55fc7ef3b2c1a238daea0e446c1e8f7
Timestamp: 1737670899 Timestamp [UCT]: 2025-01-23 22:21:39 Age [y:d:h:m:s]: 00:145:02:34:52
Block: 1203859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103444 RingCT/type: yes/0
Extra: 0112dc19c39481c2ce40daaef6c3d5a323e55fc7ef3b2c1a238daea0e446c1e8f7021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b390ba1f7ff73ce1b8297a28b665af5e5f2ca2bc723dca5a401909ad75473dee 0.600000000000 1690538 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": 1203869, "vin": [ { "gen": { "height": 1203859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b390ba1f7ff73ce1b8297a28b665af5e5f2ca2bc723dca5a401909ad75473dee" } } ], "extra": [ 1, 18, 220, 25, 195, 148, 129, 194, 206, 64, 218, 174, 246, 195, 213, 163, 35, 229, 95, 199, 239, 59, 44, 26, 35, 141, 174, 160, 228, 70, 193, 232, 247, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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