Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d74365a104f025afebcb3e2db71cef52c01b63dc229206349c1f85a78f61837

Tx prefix hash: a37037a60c6853c8eeaa8e7aa754459e7dffb1efd3badfdc0eabc63e3de1fe8e
Tx public key: 676a75bda6ef8e8481fba5d58f8512a79dc5eebc6a08e79ca57ab063d011edfe
Timestamp: 1707566633 Timestamp [UCT]: 2024-02-10 12:03:53 Age [y:d:h:m:s]: 00:349:11:25:54
Block: 954467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250141 RingCT/type: yes/0
Extra: 01676a75bda6ef8e8481fba5d58f8512a79dc5eebc6a08e79ca57ab063d011edfe0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d7e572c732436e4e8fed1e351f86e595ac3a802a449fde44435cfc60a66341a 0.600000000000 1413747 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": 954477, "vin": [ { "gen": { "height": 954467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d7e572c732436e4e8fed1e351f86e595ac3a802a449fde44435cfc60a66341a" } } ], "extra": [ 1, 103, 106, 117, 189, 166, 239, 142, 132, 129, 251, 165, 213, 143, 133, 18, 167, 157, 197, 238, 188, 106, 8, 231, 156, 165, 122, 176, 99, 208, 17, 237, 254, 2, 17, 0, 0, 0, 5, 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