Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6da24a5f6cf073a4f46b33e240ee35f31eca4f47f425ed43d144eb59da1d770d

Tx prefix hash: 9b91813e0bc21db8599e41c6aada077a0852f490309a65514bfeda39a21ff898
Tx public key: c57e2868e82dcf2910c3b16d6ede25b975407c38b80e7f1ca9126c029235ec53
Timestamp: 1729651089 Timestamp [UCT]: 2024-10-23 02:38:09 Age [y:d:h:m:s]: 00:141:19:58:34
Block: 1137538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101170 RingCT/type: yes/0
Extra: 01c57e2868e82dcf2910c3b16d6ede25b975407c38b80e7f1ca9126c029235ec530211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbefaf9a6db19f06f34ef7dbc75aa1bd8289b8fb25ec0a0c269b5d4c5441eb3b 0.600000000000 1621049 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": 1137548, "vin": [ { "gen": { "height": 1137538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbefaf9a6db19f06f34ef7dbc75aa1bd8289b8fb25ec0a0c269b5d4c5441eb3b" } } ], "extra": [ 1, 197, 126, 40, 104, 232, 45, 207, 41, 16, 195, 177, 109, 110, 222, 37, 185, 117, 64, 124, 56, 184, 14, 127, 28, 169, 18, 108, 2, 146, 53, 236, 83, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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