Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 392bc9e57d105283f4986ffc8669a49348771b8a51f33f2ae9e5decaf570560e

Tx prefix hash: a366cbaa6b40373421d3e6b5356ffc1ba1632a623b9b9227c3a3c41c007e05c5
Tx public key: 35f50beaa93e8e253be6084be278a15b639d41274dc518898b41eb349df031bd
Timestamp: 1728242912 Timestamp [UCT]: 2024-10-06 19:28:32 Age [y:d:h:m:s]: 00:183:08:10:24
Block: 1125894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130813 RingCT/type: yes/0
Extra: 0135f50beaa93e8e253be6084be278a15b639d41274dc518898b41eb349df031bd021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88a431a5598eb5ad02114ae364e093288f8499f8cd07c1f71507af57b674e052 0.600000000000 1608667 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": 1125904, "vin": [ { "gen": { "height": 1125894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88a431a5598eb5ad02114ae364e093288f8499f8cd07c1f71507af57b674e052" } } ], "extra": [ 1, 53, 245, 11, 234, 169, 62, 142, 37, 59, 230, 8, 75, 226, 120, 161, 91, 99, 157, 65, 39, 77, 197, 24, 137, 139, 65, 235, 52, 157, 240, 49, 189, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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