Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9341734cf3e49115aca0db709f5d79c47ddc691655d58f5ad1c48cf4b660b13

Tx prefix hash: 0d54ad6dcad2cc0acaf4176db6e6a3a83d69d56edb63512d40b3bb9980b2c9d2
Tx public key: 0897221d0844e952a4bbf8fb06f15495cb147add35dcc48ab3067346540268b0
Timestamp: 1651717707 Timestamp [UCT]: 2022-05-05 02:28:27 Age [y:d:h:m:s]: 03:180:05:04:32
Block: 494517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 907268 RingCT/type: yes/0
Extra: 010897221d0844e952a4bbf8fb06f15495cb147add35dcc48ab3067346540268b0021100000016a8c141c5000000000000000000

1 output(s) for total of 14.107826460000 dcy

stealth address amount amount idx
00: b1cad45a70ca7f8a6220770f6e7ae593d7f0647975dd2ee1ae7d0bf777eccba1 14.107826460000 918178 of 0

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": 494527, "vin": [ { "gen": { "height": 494517 } } ], "vout": [ { "amount": 14107826460, "target": { "key": "b1cad45a70ca7f8a6220770f6e7ae593d7f0647975dd2ee1ae7d0bf777eccba1" } } ], "extra": [ 1, 8, 151, 34, 29, 8, 68, 233, 82, 164, 187, 248, 251, 6, 241, 84, 149, 203, 20, 122, 221, 53, 220, 196, 138, 179, 6, 115, 70, 84, 2, 104, 176, 2, 17, 0, 0, 0, 22, 168, 193, 65, 197, 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