Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef4b2b3a5c5926079583afcb33a803aaafacdedfe9a59dc6baead6c172d613fd

Tx prefix hash: b9c2c0e5ba5d37691e1c3ce87580ed33d8e6be9624f20a64780aa3bdbac79764
Tx public key: 0976db615c0e1e4f4a5a95732885855c74c80efd160d2c2216a35f30ed6996b2
Timestamp: 1712514212 Timestamp [UCT]: 2024-04-07 18:23:32 Age [y:d:h:m:s]: 00:221:16:01:27
Block: 995465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158720 RingCT/type: yes/0
Extra: 010976db615c0e1e4f4a5a95732885855c74c80efd160d2c2216a35f30ed6996b20211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d15eec9364beb97c976a79156b372026d1f6e2eb5eb576c3279659190d73654c 0.600000000000 1455873 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": 995475, "vin": [ { "gen": { "height": 995465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d15eec9364beb97c976a79156b372026d1f6e2eb5eb576c3279659190d73654c" } } ], "extra": [ 1, 9, 118, 219, 97, 92, 14, 30, 79, 74, 90, 149, 115, 40, 133, 133, 92, 116, 200, 14, 253, 22, 13, 44, 34, 22, 163, 95, 48, 237, 105, 150, 178, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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