Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8674dc840a994246fc6bd6265e6e3757ae24ed5c7c8f510e4fdfa72115399ed3

Tx prefix hash: 8d8b40c1f38fb525d2f5e86237b080bcb816c26cfbefff1623877e5fcd86e5a1
Tx public key: adeeb4623c7ca99d6e3c8b9ade162fe8dc278af29453d399c635dea430f88039
Timestamp: 1762283781 Timestamp [UCT]: 2025-11-04 19:16:21 Age [y:d:h:m:s]: 00:065:00:34:48
Block: 1404987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46568 RingCT/type: yes/0
Extra: 01adeeb4623c7ca99d6e3c8b9ade162fe8dc278af29453d399c635dea430f8803902110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 156955a72b2f1e886a2255b406243223b8bce85cbcfa4cb6467944ba64ff2fb3 0.600000000000 1893356 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": 1404997, "vin": [ { "gen": { "height": 1404987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "156955a72b2f1e886a2255b406243223b8bce85cbcfa4cb6467944ba64ff2fb3" } } ], "extra": [ 1, 173, 238, 180, 98, 60, 124, 169, 157, 110, 60, 139, 154, 222, 22, 47, 232, 220, 39, 138, 242, 148, 83, 211, 153, 198, 53, 222, 164, 48, 248, 128, 57, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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