Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca75be00c0c39fe6c826dfe2ad36df34ef3d4d6f7c0b6bab4159fbd610419179

Tx prefix hash: dcb7396c11ffef33ea387002f28b80f7d073e6e43a93df15f22388193fcb4d48
Tx public key: 120aa9cd292e17b9dd103762abac4ff1dc78724348d566bba5ae485022e98dce
Timestamp: 1719638771 Timestamp [UCT]: 2024-06-29 05:26:11 Age [y:d:h:m:s]: 00:320:16:37:54
Block: 1054556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229178 RingCT/type: yes/0
Extra: 01120aa9cd292e17b9dd103762abac4ff1dc78724348d566bba5ae485022e98dce02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95cf41b6b193cf951dbb098fba84d7a595a847a593c02a43c35f88ec5d5789e3 0.600000000000 1524919 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": 1054566, "vin": [ { "gen": { "height": 1054556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95cf41b6b193cf951dbb098fba84d7a595a847a593c02a43c35f88ec5d5789e3" } } ], "extra": [ 1, 18, 10, 169, 205, 41, 46, 23, 185, 221, 16, 55, 98, 171, 172, 79, 241, 220, 120, 114, 67, 72, 213, 102, 187, 165, 174, 72, 80, 34, 233, 141, 206, 2, 17, 0, 0, 0, 3, 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