Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5049e2bb60e1d8e35cc77154235f05be6168ef5a8e75cb8bbbdbcf5305e8a737

Tx prefix hash: c09172a7c48b5bc91669525b04be96517532fa6d0dd28d41d4deb2d5df86c0b1
Tx public key: 1c78300af1d769ba1229d253caa0d9297867540adb55a0ffdd082a2c4bb76802
Timestamp: 1712398964 Timestamp [UCT]: 2024-04-06 10:22:44 Age [y:d:h:m:s]: 01:011:20:57:24
Block: 994513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269475 RingCT/type: yes/0
Extra: 011c78300af1d769ba1229d253caa0d9297867540adb55a0ffdd082a2c4bb7680202110000000e52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f269c49312f07ea9a3ff31880d073b01a25f85f2aef5a077059ff15e22d95d4 0.600000000000 1454917 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": 994523, "vin": [ { "gen": { "height": 994513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f269c49312f07ea9a3ff31880d073b01a25f85f2aef5a077059ff15e22d95d4" } } ], "extra": [ 1, 28, 120, 48, 10, 241, 215, 105, 186, 18, 41, 210, 83, 202, 160, 217, 41, 120, 103, 84, 10, 219, 85, 160, 255, 221, 8, 42, 44, 75, 183, 104, 2, 2, 17, 0, 0, 0, 14, 82, 212, 126, 148, 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