Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 475a19ece41620fa77bfda4f02626624b62ecae39a5600c5aee1ec0a7b46d3ec

Tx prefix hash: 4e34aa87d99e245866955b3326db8f4b2289a5fb0b77e4a847b72fc4d28023e4
Tx public key: 29db0c753598f82c2cc4c1ca599ab640fba5b3f00c96a52220afa33ef191dc90
Timestamp: 1736138875 Timestamp [UCT]: 2025-01-06 04:47:55 Age [y:d:h:m:s]: 00:166:02:53:48
Block: 1191227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118381 RingCT/type: yes/0
Extra: 0129db0c753598f82c2cc4c1ca599ab640fba5b3f00c96a52220afa33ef191dc900211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f1b2f8b47452d05c8396046d029a357281b995f863b00c7e421ecf82c8d2048 0.600000000000 1677750 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": 1191237, "vin": [ { "gen": { "height": 1191227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f1b2f8b47452d05c8396046d029a357281b995f863b00c7e421ecf82c8d2048" } } ], "extra": [ 1, 41, 219, 12, 117, 53, 152, 248, 44, 44, 196, 193, 202, 89, 154, 182, 64, 251, 165, 179, 240, 12, 150, 165, 34, 32, 175, 163, 62, 241, 145, 220, 144, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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