Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a0fa3a09a340e8d34616e4bea2ed9234b79b4c505cf3942847bc368f5af3366

Tx prefix hash: e819a9adea307fd5c11ab979bfbfaf4972a3f2779d5b213dd322879e8226bbe2
Tx public key: c0afc01b8e971f28cf84ab89fa171bfcdef88840b5dd0ef564f8b479c7c3a06f
Timestamp: 1718240771 Timestamp [UCT]: 2024-06-13 01:06:11 Age [y:d:h:m:s]: 00:275:14:48:17
Block: 1042976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196966 RingCT/type: yes/0
Extra: 01c0afc01b8e971f28cf84ab89fa171bfcdef88840b5dd0ef564f8b479c7c3a06f0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85592b50784b50ae629cf030bc536902c0a9f775f61c4f0b80d5f68f1853ddc6 0.600000000000 1512015 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": 1042986, "vin": [ { "gen": { "height": 1042976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85592b50784b50ae629cf030bc536902c0a9f775f61c4f0b80d5f68f1853ddc6" } } ], "extra": [ 1, 192, 175, 192, 27, 142, 151, 31, 40, 207, 132, 171, 137, 250, 23, 27, 252, 222, 248, 136, 64, 181, 221, 14, 245, 100, 248, 180, 121, 199, 195, 160, 111, 2, 17, 0, 0, 0, 1, 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