Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77dfbfbfe17de8049d92db0b1b458567c29948c19ce269cbb5d09c23f9ee4ab4

Tx prefix hash: 83a1033fe66f1ff6a1ad414dfee5c48bf4b89eb2acaa8aeeea5db7636521504f
Tx public key: 6e830410e3dea09c7153cfe73d6ac43f0eebbee059bcde3408a683c743d92acb
Timestamp: 1739104548 Timestamp [UCT]: 2025-02-09 12:35:48 Age [y:d:h:m:s]: 00:348:09:25:00
Block: 1215514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246649 RingCT/type: yes/0
Extra: 016e830410e3dea09c7153cfe73d6ac43f0eebbee059bcde3408a683c743d92acb021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a4fda1190caa7aca2e6e38fcd8de65fff8463fc06cc88675ca4a8fe0a6f2fbf 0.600000000000 1702313 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": 1215524, "vin": [ { "gen": { "height": 1215514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a4fda1190caa7aca2e6e38fcd8de65fff8463fc06cc88675ca4a8fe0a6f2fbf" } } ], "extra": [ 1, 110, 131, 4, 16, 227, 222, 160, 156, 113, 83, 207, 231, 61, 106, 196, 63, 14, 235, 190, 224, 89, 188, 222, 52, 8, 166, 131, 199, 67, 217, 42, 203, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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