Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dac7a6918b5c6316389bdb895eec5691deaa67da254651d7405c1ba47c97bf84

Tx prefix hash: a95fb7135813cb545bc6a6a579991c2d85a7dd7e7cc4415bbedddd45a85b0c2e
Tx public key: 7b278ba81ca06b366865b09e7c3e735db5e0b1c5eb837a4f6a020531f0b52ea5
Timestamp: 1703284196 Timestamp [UCT]: 2023-12-22 22:29:56 Age [y:d:h:m:s]: 01:106:03:18:25
Block: 918971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336967 RingCT/type: yes/0
Extra: 017b278ba81ca06b366865b09e7c3e735db5e0b1c5eb837a4f6a020531f0b52ea50211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 007dfdaec18f60f37b7634401269ca98e7218680e9ccadf52ab3cab979c8ebe5 0.600000000000 1376635 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": 918981, "vin": [ { "gen": { "height": 918971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "007dfdaec18f60f37b7634401269ca98e7218680e9ccadf52ab3cab979c8ebe5" } } ], "extra": [ 1, 123, 39, 139, 168, 28, 160, 107, 54, 104, 101, 176, 158, 124, 62, 115, 93, 181, 224, 177, 197, 235, 131, 122, 79, 106, 2, 5, 49, 240, 181, 46, 165, 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