Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a70df24c31672f8057a3b79beff750b0b5aad1dc76f09ee9df068b96f35e717c

Tx prefix hash: 0103843c8eb40e95853bfc33c96e2de3324ac2d479bac50e54ae6da0a2fa526d
Tx public key: 900eff92ae691b9137ca9730e80d7cac5017b5f6bbd2144c36c60e859e42a954
Timestamp: 1704253707 Timestamp [UCT]: 2024-01-03 03:48:27 Age [y:d:h:m:s]: 01:086:09:12:40
Block: 926995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322851 RingCT/type: yes/0
Extra: 01900eff92ae691b9137ca9730e80d7cac5017b5f6bbd2144c36c60e859e42a95402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e369a0f245fe4df3e55bc9aa0d978345be5c697bbe9e90fe4cc580c84c6a749e 0.600000000000 1384795 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": 927005, "vin": [ { "gen": { "height": 926995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e369a0f245fe4df3e55bc9aa0d978345be5c697bbe9e90fe4cc580c84c6a749e" } } ], "extra": [ 1, 144, 14, 255, 146, 174, 105, 27, 145, 55, 202, 151, 48, 232, 13, 124, 172, 80, 23, 181, 246, 187, 210, 20, 76, 54, 198, 14, 133, 158, 66, 169, 84, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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