Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 259b4e791f801862078639e9ed4c74b8daec11c654b0228ee82e03a4f601b036

Tx prefix hash: 8131fda360cadbf9852ce9e27f74ba25021590710c0cf9186e1a8d2cbb45f683
Tx public key: 20ee23a893366cea290e8a1bb6a846182a09b190d24b5f0bf4a6e4e470f40fbd
Timestamp: 1631715023 Timestamp [UCT]: 2021-09-15 14:10:23 Age [y:d:h:m:s]: 03:175:14:52:36
Block: 334340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 900979 RingCT/type: yes/0
Extra: 0120ee23a893366cea290e8a1bb6a846182a09b190d24b5f0bf4a6e4e470f40fbd02110000000136081066000000000000000000

1 output(s) for total of 47.884309483000 dcy

stealth address amount amount idx
00: e0450f968cc71eec34b8b6d790b340542dea74cbaa60fe7886a8b0451e2294ba 47.884309483000 689661 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": 334350, "vin": [ { "gen": { "height": 334340 } } ], "vout": [ { "amount": 47884309483, "target": { "key": "e0450f968cc71eec34b8b6d790b340542dea74cbaa60fe7886a8b0451e2294ba" } } ], "extra": [ 1, 32, 238, 35, 168, 147, 54, 108, 234, 41, 14, 138, 27, 182, 168, 70, 24, 42, 9, 177, 144, 210, 75, 95, 11, 244, 166, 228, 228, 112, 244, 15, 189, 2, 17, 0, 0, 0, 1, 54, 8, 16, 102, 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