Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d75e2b288ab945bb814195c77be11c0842d369fde0f4da212d9ee913e071e094

Tx prefix hash: 931a4f5858c7e0a94bb781b0ed7e88471531741cdc40b40e5ca5da9b778740c2
Tx public key: 379e37e75e477a4585776f98f62a1bdada6bf1f355eb2380cc3ab3177ea0b21d
Timestamp: 1711441844 Timestamp [UCT]: 2024-03-26 08:30:44 Age [y:d:h:m:s]: 01:088:09:58:55
Block: 986628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323984 RingCT/type: yes/0
Extra: 01379e37e75e477a4585776f98f62a1bdada6bf1f355eb2380cc3ab3177ea0b21d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fc769bc926c4c417771ec47cc6d1ff8693b6ed5a4a2d3c9e28bfdc33dfe2151 0.600000000000 1446859 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": 986638, "vin": [ { "gen": { "height": 986628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fc769bc926c4c417771ec47cc6d1ff8693b6ed5a4a2d3c9e28bfdc33dfe2151" } } ], "extra": [ 1, 55, 158, 55, 231, 94, 71, 122, 69, 133, 119, 111, 152, 246, 42, 27, 218, 218, 107, 241, 243, 85, 235, 35, 128, 204, 58, 179, 23, 126, 160, 178, 29, 2, 17, 0, 0, 0, 1, 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