Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d23541e45b11b56fbd8e7e389c832bb186a0a4db92851d209963d6556d73f7f

Tx prefix hash: 9aaded1609f739a36e509f89eecdb5ec5d421497059438b487aa4e3ec41c7b53
Tx public key: 79464a1a8f9396230d09e13e2be5f391e986e965e86970930e095aa808f502c2
Timestamp: 1706864058 Timestamp [UCT]: 2024-02-02 08:54:18 Age [y:d:h:m:s]: 01:041:16:05:38
Block: 948646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290855 RingCT/type: yes/0
Extra: 0179464a1a8f9396230d09e13e2be5f391e986e965e86970930e095aa808f502c202110000000110a1748f000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 7f5f0534260858dd7fadd35e291f9e8c85c3a45189cb5e058b66e5e8a507ea34 0.600010000000 1407096 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": 948656, "vin": [ { "gen": { "height": 948646 } } ], "vout": [ { "amount": 600010000, "target": { "key": "7f5f0534260858dd7fadd35e291f9e8c85c3a45189cb5e058b66e5e8a507ea34" } } ], "extra": [ 1, 121, 70, 74, 26, 143, 147, 150, 35, 13, 9, 225, 62, 43, 229, 243, 145, 233, 134, 233, 101, 232, 105, 112, 147, 14, 9, 90, 168, 8, 245, 2, 194, 2, 17, 0, 0, 0, 1, 16, 161, 116, 143, 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