Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fd2b829634259de94e6d63163dfd12515accbe61628b85cb78307224abc26d9

Tx prefix hash: 4ade90207cae171a1368ffcff09bdb26d8fdcfc4765f68afe0e5a6e43c890aa0
Tx public key: 0a4fe55e69b561e7b4770bdba112133a2de17f569e9d25b6156645194fa237b5
Timestamp: 1727899855 Timestamp [UCT]: 2024-10-02 20:10:55 Age [y:d:h:m:s]: 00:205:13:47:43
Block: 1123055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146735 RingCT/type: yes/0
Extra: 010a4fe55e69b561e7b4770bdba112133a2de17f569e9d25b6156645194fa237b502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e132d0c8f6e544c5aa7a6330944b0da8a5c4d149d39baf2c2f8447a61dbd729f 0.600000000000 1605588 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": 1123065, "vin": [ { "gen": { "height": 1123055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e132d0c8f6e544c5aa7a6330944b0da8a5c4d149d39baf2c2f8447a61dbd729f" } } ], "extra": [ 1, 10, 79, 229, 94, 105, 181, 97, 231, 180, 119, 11, 219, 161, 18, 19, 58, 45, 225, 127, 86, 158, 157, 37, 182, 21, 102, 69, 25, 79, 162, 55, 181, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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