Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f077eb0895c824d2e237dd16b3c08b7dae69a99cc99ef463eb4e1ff2490b78b0

Tx prefix hash: 805a28ac2f17ad5478251899e114214fc86394975659dc0d58fa5c4f29b8a016
Tx public key: f0ec40ced51e2de4f5c74887f3f4e54cea1db548e6984e645dc1fd71bd7e6ca0
Timestamp: 1711014888 Timestamp [UCT]: 2024-03-21 09:54:48 Age [y:d:h:m:s]: 00:363:09:29:36
Block: 983087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259822 RingCT/type: yes/0
Extra: 01f0ec40ced51e2de4f5c74887f3f4e54cea1db548e6984e645dc1fd71bd7e6ca00211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f308b0acd216db22163b0ee1b53d321b2f2102d80240cc69411b36a192eb20e 0.600000000000 1443208 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": 983097, "vin": [ { "gen": { "height": 983087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f308b0acd216db22163b0ee1b53d321b2f2102d80240cc69411b36a192eb20e" } } ], "extra": [ 1, 240, 236, 64, 206, 213, 30, 45, 228, 245, 199, 72, 135, 243, 244, 229, 76, 234, 29, 181, 72, 230, 152, 78, 100, 93, 193, 253, 113, 189, 126, 108, 160, 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