Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c43f207ffbdbe9f724ff31c412673ddd953265f85c1a9d36c328193d207b7934

Tx prefix hash: ed09c1590a980d243a6175d589f7ae6297f3ed427643c3a7978e42ed8ef0f09c
Tx public key: 21469cc113f44782e7db1e76e96f49a6c31a3575025d948b70edb4d31a77aaba
Timestamp: 1716812464 Timestamp [UCT]: 2024-05-27 12:21:04 Age [y:d:h:m:s]: 00:293:23:56:27
Block: 1031142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210123 RingCT/type: yes/0
Extra: 0121469cc113f44782e7db1e76e96f49a6c31a3575025d948b70edb4d31a77aaba0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9e85eaad63d69c37a8ae8edb0944c783db352ac72e93e425f9e81f98bf3211c 0.600000000000 1499513 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": 1031152, "vin": [ { "gen": { "height": 1031142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9e85eaad63d69c37a8ae8edb0944c783db352ac72e93e425f9e81f98bf3211c" } } ], "extra": [ 1, 33, 70, 156, 193, 19, 244, 71, 130, 231, 219, 30, 118, 233, 111, 73, 166, 195, 26, 53, 117, 2, 93, 148, 139, 112, 237, 180, 211, 26, 119, 170, 186, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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