Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51fd30aca48d28f84b6947baac7178224ac4779dfdd22f8cc679d134f45bbe58

Tx prefix hash: 697f9f3c1c66c2b6f91e9267b3f8973a62ff8f7dc4545837b8bc236041cbb8c0
Tx public key: f37c8e8805e8df6e2f9c8336da1c7ab14e85fd5050d853edee400a86aaf3efdf
Timestamp: 1730876899 Timestamp [UCT]: 2024-11-06 07:08:19 Age [y:d:h:m:s]: 00:145:10:36:16
Block: 1147637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103777 RingCT/type: yes/0
Extra: 01f37c8e8805e8df6e2f9c8336da1c7ab14e85fd5050d853edee400a86aaf3efdf0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81f5e15d9a457464fdddce70260722a29180c984b1fd49d586821bb4c0fdf3b9 0.600000000000 1632336 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": 1147647, "vin": [ { "gen": { "height": 1147637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81f5e15d9a457464fdddce70260722a29180c984b1fd49d586821bb4c0fdf3b9" } } ], "extra": [ 1, 243, 124, 142, 136, 5, 232, 223, 110, 47, 156, 131, 54, 218, 28, 122, 177, 78, 133, 253, 80, 80, 216, 83, 237, 238, 64, 10, 134, 170, 243, 239, 223, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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