Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c667ca3d67590665c65769dfb0d8529032558b0785fd6d2430c3cabc5c91265

Tx prefix hash: d26c9bededf06f97bd854c4aedf72ddaea53b0f96b13f8389f6f070aae494cdf
Tx public key: fba69169906fd441dcf15e4cc833cb2ca41dd283d0d463d47e2f0c4e29d68a11
Timestamp: 1706611180 Timestamp [UCT]: 2024-01-30 10:39:40 Age [y:d:h:m:s]: 01:085:16:06:20
Block: 946543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322319 RingCT/type: yes/0
Extra: 01fba69169906fd441dcf15e4cc833cb2ca41dd283d0d463d47e2f0c4e29d68a1102110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26cf5c3bce00782c6cf43a0aa30797dca3bd86f92fe06c8e495ce398eca409ba 0.600000000000 1404875 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": 946553, "vin": [ { "gen": { "height": 946543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26cf5c3bce00782c6cf43a0aa30797dca3bd86f92fe06c8e495ce398eca409ba" } } ], "extra": [ 1, 251, 166, 145, 105, 144, 111, 212, 65, 220, 241, 94, 76, 200, 51, 203, 44, 164, 29, 210, 131, 208, 212, 99, 212, 126, 47, 12, 78, 41, 214, 138, 17, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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