Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4295752a0d7b55e55e83fcd7556dbd93e336886f7ac59fff9b91363f8e4e3915

Tx prefix hash: 32512aac9d5a8f05fef97b240cb56765d7cb2b4cc86131bcb9aa3a15d7922be0
Tx public key: 531ca4976eaedb8548c222fe33342170e4f0069d7c898a06940c2f14949ce723
Timestamp: 1723298048 Timestamp [UCT]: 2024-08-10 13:54:08 Age [y:d:h:m:s]: 00:279:23:53:09
Block: 1084901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200026 RingCT/type: yes/0
Extra: 01531ca4976eaedb8548c222fe33342170e4f0069d7c898a06940c2f14949ce723021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ba80106302b3fda0add5b8adea9a4cbb6790e64fb57688c31b52508fb7a38e0 0.600000000000 1559340 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": 1084911, "vin": [ { "gen": { "height": 1084901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ba80106302b3fda0add5b8adea9a4cbb6790e64fb57688c31b52508fb7a38e0" } } ], "extra": [ 1, 83, 28, 164, 151, 110, 174, 219, 133, 72, 194, 34, 254, 51, 52, 33, 112, 228, 240, 6, 157, 124, 137, 138, 6, 148, 12, 47, 20, 148, 156, 231, 35, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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