Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2aff455509b50fd6be490866a3bbc0f0a7454f829ae24ee1162e74f85b144e9a

Tx prefix hash: 1877d4396c580466f017dcdacb2d06cb3bc1aa968a881d05b4d120dcbef32469
Tx public key: 54697e9f0b0249f95d14ca9f5c549d9b4adb362aee344e5fc8347d95f685102a
Timestamp: 1722160066 Timestamp [UCT]: 2024-07-28 09:47:46 Age [y:d:h:m:s]: 01:101:13:26:53
Block: 1075468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331057 RingCT/type: yes/0
Extra: 0154697e9f0b0249f95d14ca9f5c549d9b4adb362aee344e5fc8347d95f685102a021100000014e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2baa97fe4a25c0993ed6753674aea6926c989ba851f0f0b0c9435eee3eebe32e 0.600000000000 1547995 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": 1075478, "vin": [ { "gen": { "height": 1075468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2baa97fe4a25c0993ed6753674aea6926c989ba851f0f0b0c9435eee3eebe32e" } } ], "extra": [ 1, 84, 105, 126, 159, 11, 2, 73, 249, 93, 20, 202, 159, 92, 84, 157, 155, 74, 219, 54, 42, 238, 52, 78, 95, 200, 52, 125, 149, 246, 133, 16, 42, 2, 17, 0, 0, 0, 20, 233, 20, 221, 21, 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