Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf5948d38098c542b9f1ce4ee781f741e1dac0426e134804aeaab64a434948f5

Tx prefix hash: f6157b7ee8d421c17ea683e9528dd24cd6217182666dced0ce058f2b5b0dd60e
Tx public key: 1ff18ccea0554264556022bf098d67fb02b0bfc1abcb372b0a01e90d0bdc2899
Timestamp: 1706096212 Timestamp [UCT]: 2024-01-24 11:36:52 Age [y:d:h:m:s]: 01:145:21:38:31
Block: 942255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365302 RingCT/type: yes/0
Extra: 011ff18ccea0554264556022bf098d67fb02b0bfc1abcb372b0a01e90d0bdc28990211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd3ec0a84a3b468a71faca5e4fe8ce904e7f4c2f39c0fd3542cd8d630a144ccb 0.600000000000 1400421 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": 942265, "vin": [ { "gen": { "height": 942255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd3ec0a84a3b468a71faca5e4fe8ce904e7f4c2f39c0fd3542cd8d630a144ccb" } } ], "extra": [ 1, 31, 241, 140, 206, 160, 85, 66, 100, 85, 96, 34, 191, 9, 141, 103, 251, 2, 176, 191, 193, 171, 203, 55, 43, 10, 1, 233, 13, 11, 220, 40, 153, 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